Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue 3632 - modify float is float to do a bitwise compare #724

Merged
merged 1 commit into from Feb 18, 2012

Conversation

yebblies
Copy link
Member

Make 'is' between floats and structs containing floats consistent at run-time and compile-time.

This fixes the padding issue of the previous fix.

http://d.puremagic.com/issues/show_bug.cgi?id=3632

@9rnsr This includes your fix for 3789 from pull #387 - if you can put those changes into a single commit I'll rebase on top of that instead of copying your fix.

Make 'is' between floats and structs containing floats consistent at run-time and compile-time.

This fixes the padding issue of the previous fix.
@yebblies
Copy link
Member Author

Actually never mind it needs phobos changes too, I'll just remove the == test cases.

WalterBright added a commit that referenced this pull request Feb 18, 2012
Issue 3632 - modify float is float to do a bitwise compare
@WalterBright WalterBright merged commit b558967 into dlang:master Feb 18, 2012
@@ -204,6 +204,9 @@ int StructDeclaration::needOpEquals()
if (hasIdentityEquals)
goto Lneed;

if (isUnionDeclaration())
goto Ldontneed;

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reverted the changes to clone.c, as they broke Phobos std.algorithm unittests.

@WalterBright
Copy link
Member

Had to revert the rest, too. xtest46.d fails on OSX. Patch needs more work & testing.

@yebblies
Copy link
Member Author

Yeah sorry, I needed to cut out the == part and hadn't done it yet. Doing it now.

@yebblies
Copy link
Member Author

#730

@braddr
Copy link
Member

braddr commented Feb 18, 2012

this pull request also clearly failed in the pull tester so was a bad candidate for merging:

http://d.puremagic.com/test-results/pull-history.ghtml?projectid=1&pullid=724

@yebblies
Copy link
Member Author

Yeah, even when the master branch is broken, the pull history should show that the pull passed with earlier versions.

if (walterReviewPassed)
{
    if (pullTesterState == passing)
        pull();
    else if (masterTesterState == failing && pullTesterHistory == good)
        pull();
    else
        dontPull();
}
else
{
    rejectPull();
}

@braddr
Copy link
Member

braddr commented Feb 18, 2012

if masterState == failing goFixMasterAndQuitLookingAtPulls();

@yebblies
Copy link
Member Author

There is still a delay between master getting fixed and the pulls moving back from red to green.

braddr pushed a commit to braddr/dmd that referenced this pull request Oct 22, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants